07. Identifying Requirements
Identifying Requirements
Identifying Requirements
ND036 C1 L1 07 Identifying Requirements
Identifying Requirements Quiz
SOLUTION:
FalseIdentifying Requirements Quiz 2
SOLUTION:
FalseUntitled
Summary
Once a requirement has been identified, it gets documented in a PRD (Product Requirements Document). Keep in mind that identifying requirements is a much more active and involved process than just “gathering.” It’s important that PMs understand the problem and why a specific requirement exists.
Identifying Requirements can happen through a variety of channels:
- Research
- Prototyping
- Input from users / customers
- Input from cross functional partners
And two common challenges that come up when identifying requirements are:
- Never be sure that all requirements have been identified
- Users might not be able to tell you what the product should do (ie: the requirement). Instead it’s better to focus on understanding the problem the user is facing and their needs. Ask why. Then ask why again. And keep asking why until you get to a deeper understanding.
Identifying Requirements - Further Research